Parent Entity Options

This is the name of the entity. Once created, the name of the entity cannot be modified.

This is the description of the entity. It is important when building your parent and child entities to briefly describe the entity.

This field zooms to the Rights list in SmartSolve. This is the right that later must be assigned to any user in the system to allow the user to create this record. See Creating New Entity Rights for additional information.

This field zooms to the Rights list in SmartSolve. This is the right that must be assigned to any user in the system to allow the user to view this record. See Creating New Entity Rights for additional information.

This field zooms to the Rights list in SmartSolve. This is the right that must be assigned to any user in the system to allow the user to manage this record. See Creating New Entity Rights for additional information.

This field zooms to the Rights list in SmartSolve. This is the right that must be assigned to any user in the system to allow the user to delete this record. See Creating New Entity Rights for additional information

Since table and views in the same schema cannot have the same name, this field automatically displays the name of the entity created with a V_ placed at the beginning of the value to specify whether the value is a view or a table.

The runtime table contains the schema that must be generated for the storage of the entity created. SmartSolve comes with the following three Generic (GRC) database tables for Parent Entities in which your newly added views will later be applied to:

• GRC_RUN_GT1
• GRC_RUN_GT2
• GRC_RUN_GT3

The system can store and fetch the data based on an entity identifier and not based on the underlying table. You can use any of these three tables for your entities; however, if you want to use your own runtime tables, please contact Pilgrim Quality Solutions for options for configuring specialized entities using the Schema Generator provided by Pilgrim.

Specifies "Yes" for parent entity.

The Object Table Name is?

Here are several helpful guidelines for naming objects and their parts:

• Use full, descriptive, pronounceable names (or well-known abbreviations).
• Use consistent naming rules.
• Use the same name to describe the same entity or attribute across tables.
• When naming objects, balance the objective of keeping names short and easy to use with the objective of making names as descriptive as possible. When in doubt, choose the more descriptive name, because the objects in the database may be used by many people over a period of time. Your counterpart ten years from now may have difficulty understanding a table column with a name like pmdd instead of payment_due_date.
• Using consistent naming rules helps users understand the part that each table plays in your application. One such rule might be to begin the names of all tables belonging to the FINANCE application with fin_.
• Use the same names to describe the same things across tables. For example, the department number columns of the sample employees and departments tables are both named department_id.

Validate against a parent record type entity

Validate against a parent record type entity and numbering scheme tied to that entity

Primary status of the record:

• ABORTED
• CLOSED
• INWORKS
• OPEN
• ROUTED
• VOID

Secondary status of the record

Phase of the record

Title of the record

Record Owner Code (Internal Actor or Person)

Record Owner Name (Internal Actor or Person)

The number of relations that entity has with other entities (automatically tracked when spawning one workflow from another workflow)

Record Closed Date

Date the record was voided by a user